|
Software project management is the art and science of planning and leading software projects. It is a sub-discipline of project management in which software projects are planned, implemented, monitored and controlled. == History == In the 1970s and 1980s, the software industry grew very quickly, as computer companies quickly recognized the relatively low cost of software production compared to hardware production and circuitry. To manage new development efforts, companies applied the established project management methods, but project schedules slipped during test runs, especially when confusion occurred in the gray zone between the user specifications and the delivered software. To be able to avoid these problems, ''software'' project management methods focused on matching user requirements to delivered products, in a method known now as the waterfall model. As the industry has matured, analysis of software project management failures has shown that the following are the most common causes:〔("Why Software Fails" ), in ''IEEE Spectrum''〕〔(Producing Open Source Software: How to Run a Successful Free Software Project ) (e-book, freely downloadable), by Karl Fogel〕〔Robert Frese and Vicki Sauter, "Improving your odds for software project success," ''IEEE Engineering Management Review,'' Vol. 42, No. 4, Fourth Quarter, Dec 2014〕 # Insufficient end-user involvement # Poor communication among customers, developers, users and project managers # Unrealistic or unarticulated project goals # Inaccurate estimates of needed resources # Badly defined or incomplete system requirements and specifications # Poor reporting of the project's status # Poorly managed risks # Use of immature technology # Inability to handle the project's complexity # Sloppy development practices # Stakeholder politics (e.g. absence of executive support, or politics between the customer and end-users) # Commercial pressures The first five items in the list above show the difficulties articulating the needs of the client in such a way that proper resources can deliver the proper project goals. Specific software project management tools are useful and often necessary, but the true art in software project management is applying the correct method and then using tools to support the method. Without a method, tools are worthless. Since the 1960s, several proprietary software project management methods have been developed by software manufacturers for their own use, while computer consulting firms have also developed similar methods for their clients. Today software project management methods are still evolving, but the current trend leads away from the waterfall model to a more cyclic project delivery model that imitates a software development process. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「software project management」の詳細全文を読む スポンサード リンク
|